View AT32AP7002-CTUR_1638065.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

features ? high performance, low power avr ? 32 32-bit microcontroller ? 210 dmips throughput at 150 mhz ? 16 kb instruction cache and 16 kb data caches ? memory management unit enab ling use of operating systems ? single-cycle risc instruction set including simd and dsp instructions ? java hardware acceleration ? pixel co-processor ? pixel co-processor for video acceler ation through color-space conversion (yuv<->rgb), image scalin g and filtering, quarter pixel motion compensation ? multi-hierarchy bus system ? high-performance data transfers on separate buses for increased performance ? data memories ? 32kbytes sram ? external memory interface ? sdram, dataflash ? , sram, multi media card (mmc), secure digital (sd), ? compact flash, smart media, nand flash ? direct memory access controller ? external memory access without cpu intervention ? interrupt controller ? individually maskable interrupts ? each interrupt request has a programm able priority and autovector address ? system functions ? power and clock manager ? crystal oscillator wit h phase-lock-loop (pll) ? watchdog timer ? real-time clock ? 6 multifunction timer/counters ? three external clock inputs, i/o pins, pwm, capture and various counting capabilities ? 4 universal synchronous/asynchrono us receiver/transmitters (usart) ? 115.2 kbps irda modulation and demodulation ? hardware and software handshaking ? 3 synchronous serial protocol controllers ? supports i2s, spi and gene ric frame-based protocols ? two-wire interface ? sequential read/write operations, philips? i2c? compatible ? liquid crystal disp lay (lcd) interface ? supports tft displays ? configurable pixel resolution supporting qcif/qvga/vga/svga configurations. ? image sensor interface ? 12-bit data interface for cmos cameras ? universal serial bus (usb) 2.0 high speed (480 mbps) device ? on-chip transceivers with physical interface ? 16-bit stereo audio bitstream dac ? sample rates up to 50 khz ? on-chip debug system ? nexus class 3 ? full speed, non-intrusive data and program trace ? runtime control and jtag interface ? package/pins ? at32ap7002: 196-ball ctbga ? power supplies ? 1.65v to1.95v vddcore ? 3.0v to 3.6v vddio 32054fs-avr32-09/09 avr ? 32 32-bit microcontroller at32ap7002 preliminary summary
2 32054fs?avr32?09/09 at32ap7002 1. part description the at32ap7002 is a complete system-on-chip application processor with an avr32 risc processor achieving 210 dmips running 150 mhz. avr32 is a high-performance 32-bit risc microprocessor core, designed for cost-sensitive embedded applications, with particular empha- sis on low power consumption, high code density and high application performance. at32ap7002 implements a memory management unit (mmu) and a flexible interrupt controller supporting modern operating systems and real-time operating systems. the processor also includes a rich set of dsp and simd instructio ns, specially designed fo r multimedia and telecom applications. at32ap7002 incorporates sram memories on-chip for fast and secure access. for applica- tions requiring additional memory, external 16-bit sram is accessible. additionally, an sdram controller provides off-chip volat ile memory access as well as cont rollers for all industry standard off-chip non-volatile memories, like compact flash, multi media card (mmc), secure digital (sd)-card, smartcard, nand flash and atmel dataflash?. the direct memory access controller for all the serial peripherals enables data transfer between memories without processor intervention. this reduces the processor overhead when transfer- ring continuous and large data streams between modules in the mcu. the timer/counters includes three identical 16-bit timer/counter channels. each channel can be independently programmed to perform a wide range of functions including frequency measure- ment, event counting, interval measurement, pulse generation, delay timing and pulse width modulation. at32ap7002 also features an onboard lcd controller, supporting single and double scan monochrome and color passive stn lcd modul es and single scan acti ve tft lcd modules. on monochrome stn displays, up to 16 gray shades are supported using a time-based dither- ing algorithm and frame rate control (frc) method. this method is also used in color stn displays to generate up to 4096 colors. the lcd controller is programmable for supporting resolutions up to 2048 x 2048 with a pixel depth from 1 to 24 bits per pixel. a pixel co-processor provides color space conv ersions for images and video, in addition to a wide variety of hardware filter support the media-independent interface (mii) and reduced mii (rmii) 10/100 ethernet mac modules provides on-chip solutions for network-connected devices. synchronous serial controllers provide easy ac cess to serial communication protocols, audio standards like i2s and frame-based protocols. the java hardware acceleration implementation in avr32 allows for a very high-speed java byte-code execution. avr32 implements java in structions in hardware, reusing the existing risc data path, which allows for a near-zero hardware overhead and cost with a very high performance. the image sensor interface supports cameras with up to 12-bit data buses. ps2 connectivity is provided for standa rd input devices like mice and keyboards.
3 32054fs?avr32?09/09 at32ap7002 at32ap7002 integrates a class 3 nexus 2.0 on -chip debug (ocd) system, with non-intrusive real-time trace, full-speed read/write memory access in addition to basic runtime control. the c-compiler is closely linked to the architecture and is able to utilize code optimization fea- tures, both for size and speed.
4 32054fs?avr32?09/09 at32ap7002 2. blockdiagram figure 2-1. blockdiagram data[11..0] hsync vsync pclk ap cpu nexus class 3 ocd instr cache data cache timer/counter 0/1 interrupt controller real time counter peripheral dma controller intram0 intram1 hsb-pb bridge b hsb-pb bridge a s m m m s s s m external interrupt controller high speed bus matrix parallel input/output controllers pixel coprocessor parallel input/output controllers reset_n pa pb pc pd pe a [ 2 . . 0 ] b [ 2 . . 0 ] clk[2..0] e x t i n t [ 7 . . 0 ] k p s [ 7 . . 0 ] nmi_n g c l k [ 3 . . 0 ] xin32 xout32 xin0 xout0 pa pb pc pd pe external bus interface (sdram & static memory controller & ecc) ncs[5,4,2] cfrnw, cfce1, cfce2, addr[23..25] nwait data[15..0] usb interface dma d- d+ 32 khz osc osc0 pll0 ps2 interface serial peripheral interface 0/1 two-wire interface pdc miso, mosi npcs[3..1] scl sda usart0 usart1 usart2 usart3 pdc rxd txd clk rts, cts synchronous serial controller 0/1/2 pdc tx_clock, tx_frame_sync rx_data tx_data rx_clock, rx_frame_sync watchdog timer xin1 xout1 osc1 pll1 sck jtag interface mcko mdo[5..0] mseo[1..0] evti_n evto_n tck tdo tdi tms power manager reset controller sleep controller clock controller clock generator configuration registers bus memory management unit pb pb hsb hs b pba pbb npcs0 m s clock[1..0] data[1..0] hsb-hsb bridge trst_n data[31..16] oscen_n pll0 pll1 dma controller s m m audio bitstream dac dma multimedia card interface dma ac97 controller dma s c l k s d i s s y n c s d o c l k cmd data[7..0] d a t a 0 d a t a 1 d a t a 0 n d a t a 1 n pulse width modulation controller pwm0 pwm1 pwm2 pwm3 image sensor interface m lcd contro ller dma m s vsync, hsync, pwr, pclk, mode, dval, cc, data[22..0], gpl[7..0] ras, cas, sdwe, nandoe, nandwe, sdck, sdcke, nwe3, nwe1, nwe0, nrd, ncs[3,1,0], addr[22..0]
5 32054fs?avr32?09/09 at32ap7002 2.0.1 avr32ap cpu ? 32-bit load/store avr32b risc architecture. ? up to 15 general-purpose 32-bit registers. ? 32-bit stack pointer, program counter and link register reside in register file. ? fully orthogonal instruction set. ? privileged and unprivileged modes enabling efficient and secure operating systems. ? innovative instruction set together with variable instruction length ensu ring industry leading code density. ? dsp extention with saturating arithmetic, and a wide variet y of multiply instructions. ? simd extention for media applications. ? 7 stage pipeline allows one instruction per clock cycle for most instructions. ? java hardware acceleration. ? byte, half-word, word and double word memory access. ? unaligned memory access. ? shadowed interrupt context for int3 an d multiple interrupt priority levels. ? dynamic branch prediction and return address stac k for fast change-of-flow. ? coprocessor interface. ? full mmu allows for operating systems with memory protection. ? 16kbyte instruction and 16kbyte data caches. ? virtually indexed, physically tagged. ? 4-way associative. ? write-through or write-back. ? nexus class 3 on-chip debug system. ? low-cost nanotrace supported. 2.0.2 pixel coprocessor (pico) ? coprocessor coupled to the avr3 2 cpu core through the tcb bus. ? coprocessor number one on the tcb bus. ? three parallel vector multiplicati on units (vmu) where each unit can: ? multiply three pixel componen ts with three coefficients. ? add the products from the multiplications together. ? accumulate the result or add an o ffset to the sum of the products. ? can be used for accelerating: ? image color space conversion. ?configurable conver sion coefficients. ? supports packed and planar input and output formats. ? supports subsampled input color spaces (i.e 4:2:2, 4:2:0). ? image filtering/scaling. ? configurable filter coefficients. ? throughput of one sample per cycle for a 9-tap fir filter. ? can use the built-in accumulator to extend the fir filter to more than 9-taps. ? can be used for bilinear/bicubic interpolations. ? mpeg-4/h.264 quarter pi xel motion compensation. ? flexible input pixel selector. ? can operate on numerous different image storage formats. ? flexible output pixel inserter. ? scales and saturates the results back to 8-bit pixel values. ? supports packed and planar output formats.
6 32054fs?avr32?09/09 at32ap7002 ? configurable coefficien ts with flexible fixe d-point representation. 2.0.3 debug and test system ? ieee1149.1 compliant jtag and boundary scan ? direct memory access and programming capabilities through jtag interface ? extensive on-chip debug features in compliance with ieee-isto 5001-2003 (nexus 2.0) class 3 ? auxiliary port for high-speed trace information ? hardware support for 6 program and 2 data breakpoints ? unlimited number of softw are breakpoints supported ? advanced program, data, ownership, and watchpoint trace supported 2.0.4 dma controller ? 2 hsb master interfaces ? 3 channels ? software and hardware handshaking interfaces ? 11 hardware handshaking interfaces ? memory/non-memory periph erals to memory/non-mem ory peripherals transfer ? single-block dma transfer ? multi-block dma transfer ? linked lists ? auto-reloading ? contiguous blocks ? dma controller is always the flow controller ? additional features ? scatter and gather operations ? channel locking ? bus locking ? fifo mode ? pseudo fly-by operation 2.0.5 peripheral dma controller ? transfers from/to peripheral to/from any memory space without interven tion of the processor. ? next pointer support, forbids strong real -time constraints on buffer management. ? eighteen channels ? two for each usart ? two for each serial synchronous controller ? two for each serial peripheral interface 2.0.6 bus system ? hsb bus matrix with 10 masters and 8 slaves handled ? handles requests from the cpu icache, cpu d cache, hsb bridge, hisi, usb 2.0 controller, lcd controller, dma controller 0, dma controller 1, and to internal sram 0, internal sram 1, pb a, pb b, ebi and, usb.
7 32054fs?avr32?09/09 at32ap7002 ? round-robin arbitration (three modes supported: no default master, last accessed default master, fixed default master) ? burst breaking with slot cycle limit ? one address decoder provided per master ? 2 peripheral buses allowing each bu s to run on different bus speeds. ? pb a intended to run on low clock speed s, with peripherals co nnected to the pdc. ? pb b intended to run on higher clock spee ds, with peripherals connected to the dmaca. ? hsb-hsb bridge providing a low-speed hs b bus running at the same speed as pba ? allows pdc transfers between a low-speed pb bus and a bus matrix of higher clock speeds an overview of the bus system is given in figure 1-1 on page 1 . all modules connected to the same bus use the same clock, but the clock to each module can be individually shut off by the power manager. the figure identifies the number of master and slave interfaces of each module connected to the hsb bus, and which dma controller is connected to which peripheral.
8 32054fs?avr32?09/09 at32ap7002 2.1 package and pinout avr32ap7002 figure 2-2. 196 ctbga pinout top view bottom view ball a1 avr32 a b c d e f g h j k l m n p a b c d e f g h j k l m n p 14 13 12 11 10 9 8 7 6 5 4 3 2 1 1413121110 9 8 7 6 5 4 3 2 1 table 2-1. ctbga196 package pinout a1..t8 12345678 a px49 px48 px47 avddpll pc28 pc23 pc20 pb22 b px50 gnd vddio pll0 pll1 xin32 pc22 pb23 c px51 pd01 px05 gnd agndpll xout32 pc29 pc21 d px32 pd00 vddio px02 xin0 xout0 agndosc pc30 e px33 px00 px04 gnd pd07 avddosc oscen_n pc31 f px01 px03 vddcore pd04 pd09 tdi reset_n vddcore g pd05 pd08 pd06 tdo pa04 pa02 pa08 px22 h tms trst_n tck evti_n pb24 pa10 pa14 px38 j pa 0 1 pa 0 3 pa 0 0 v d d i o g n d pa 0 9 pa 1 8 g n d k pa 0 5 pa 1 1 pa 1 2 pa 1 6 g n d g n d pa 2 6 wa k e _ n l pb25 pa21 pa19 gnd vddio vddio pa25 pa29 m pa13 pa22 pa23 pd17 avddusb vddcore vbg pa30 n pa15 pa20 pd12 pd15 pd16 agndusb fsdp hsdp p pa17 pa24 pd13 pd14 xin1 xout1 fsdm hsdm
9 32054fs?avr32?09/09 at32ap7002 table 2-2. ctbga196 package pinout a9..t16 9 1011121314 a pb18 pb16 pb11 pb08 pb05 pb04 b pb21 pb17 pb12 pb09 pb06 pb03 c pa06 pb19 pb14 pb10 pb07 pb02 d vddio pb20 pb15 pb13 gnd pb01 e pa07 gnd pb00 px44 vddio px45 f px42 gnd gnd px43 px46 px40 g px30 px25 px31 vddio vddcore px39 h pa28 px20 px28 px29 vddcore px26 j pb27 px37 px23 px27 px21 px24 k pb28 px15 px36 px19 px34 px18 l px41 gnd px07 vddio gnd px35 m px53 px06 px11 px12 px17 px14 n pb26 vddio px09 pb29 px16 px13 p pa27 pa31 px52 px08 px10 pb30
10 32054fs?avr32?09/09 at32ap7002 3. signals description the following table gives details on the signal name classified by peripheral. the pinout multi- plexing of these signals is given in the perip heral muxing table in the peripherals chapter. table 3-1. signal description list signal name function type active level comments power avddpll pll power supply power 1.65 to 1.95 v avddusb usb power supply power 1.65 to 1.95 v avddosc oscillator power supply power 1.65 to 1.95 v vddcore core power supply power 1.65 to 1.95 v vddio i/o power supply power 3.0 to 3.6v agndpll pll ground ground agndusb usb ground ground agndosc oscillator ground ground gnd ground ground clocks, oscillators, and pll?s xin0, xin1, xin32 crystal 0, 1, 32 input analog xout0, xout1, xout32 crystal 0, 1, 32 output analog pll0, pll1 pll 0,1 filter pin analog jtag tck test clock input tdi test data in input tdo test data out output tms test mode select input trst_n test reset input low auxiliary port - aux mcko trace data output clock output mdo0 - mdo5 trace data output output mseo0 - mseo1 trace frame control output evti_n event in input low
11 32054fs?avr32?09/09 at32ap7002 evto_n event out output low power manager - pm gclk0 - gclk4 generic clock pins output oscen_n oscillator enable input low reset_n reset pin input low wake_n wake pin input low external interrup t controller - eic extint0 - extint3 external interrupt pins input nmi_n non-maskable interrupt pin input low ac97 controller - ac97c sclk ac97 clock signal input sdi ac97 receive signal output sdo ac97 transmit signal output sync ac97 frame synchronization signal input audio bitstream dac - abdac data0 - data1 d/a data out output datan0 - datan1 d/a inverted data out output external bus interface - ebi px0 - px53 i/o controlled by ebi i/o addr0 - addr25 address bus output cas column signal output low cfce1 compact flash 1 chip enable output low cfce2 compact flash 2 chip enable output low cfrnw compact flash read not write output data0 - data31 data bus i/o nandoe nand flash output enable output low nandwe nand flash write enable output low ncs0 - ncs5 chip select output low table 3-1. signal description list signal name function type active level comments
12 32054fs?avr32?09/09 at32ap7002 nrd read signal output low nwait external wait signal input low nwe0 write enable 0 output low nwe1 write enable 1 output low nwe3 write enable 3 output low ras row signal output low sda10 sdram address 10 line output sdck sdram clock output sdcke sdram clock enable output sdwe sdram write enable output low image sensor interface - isi data0 - data11 image sensor data input hsync horizontal synchronization input pclk image sensor data clock input vsync vertical synchronization input lcd controller - lcdc cc lcd contrast control output data0 - data23 lcd data bus input dval lcd data valid output gpl0 - gpl7 lcd general purpose lines output hsync lcd horizontal synchronization output mode lcd mode output pclk lcd clock output pwr lcd power output vsync lcd vertical synchronization output multimedia card interface - mci clk multimedia card clock output cmd0 - cmd1 multimedia card command i/o table 3-1. signal description list signal name function type active level comments
13 32054fs?avr32?09/09 at32ap7002 data0 - data7 multimedia card data i/o parallel input/output - pioa, piob, pioc, piod pa0 - pa31 parallel i/o controller pioa i/o pb0 - pb30 parallel i/o controller piob i/o pc20 - pc23/ pc28 - pc31 parallel i/o controller pioc i/o pd0 - pd17 parallel i/o controller piod i/o ps2 interface - psif clock0 - clock1 ps2 clock input data0 - data1 ps2 data i/o serial peripheral in terface - spi0, spi1 miso master in slave out i/o mosi master out slave in i/o npcs0 - npcs3 spi peripheral chip select i/o low sck clock output synchronous serial contro ller - ssc0, ssc1, ssc2 rx_clock ssc receive clock i/o rx_data ssc receive data input rx_frame_sync ssc receive frame sync i/o tx_clock ssc transmit clock i/o tx_data ssc transmit data output tx_frame_sync ssc transmit frame sync i/o dma controller - dmaca dmarq0 - dmarq3 dma requests input timer/counter - timer0, timer1 a0 channel 0 line a i/o a1 channel 1 line a i/o a2 channel 2 line a i/o b0 channel 0 line b i/o table 3-1. signal description list signal name function type active level comments
14 32054fs?avr32?09/09 at32ap7002 b1 channel 1 line b i/o b2 channel 2 line b i/o clk0 channel 0 external clock input input clk1 channel 1 external clock input input clk2 channel 2 external clock input input two-wire interface - twi scl serial clock i/o sda serial data i/o universal synchronous asynchronous receiver transmitter - usart0, usart1, usart2, usart3 clk clock i/o cts clear to send input rts request to send output rxd receive data input txd transmit data output pulse width modulator - pwm pwm0 - pwm3 pwm output pins output usb interface - usba hsdm high speed usb interface data - analog fsdm full speed usb interface data - analog hsdp high speed usb interface data + analog fsdp full speed usb interface data + analog vbg usb bandgap analog connected to a 6810 ohm 0.5% resistor to gound and a 10 pf capacitor to ground. table 3-1. signal description list signal name function type active level comments
15 32054fs?avr32?09/09 at32ap7002 4. power considerations 4.1 power supplies the at32ap7002 has several types of power supply pins: ? vddcore pins: power the core , memories, and peripherals. voltage is 1.8v nominal. ? vddio pins: power i/o lines. voltage is 3.3v nominal. ? vddpll pin: powers the pll. voltage is 1.8v nominal. ? vddusb pin: powers the usb. voltage is 1.8v nominal. ? vddosc pin: powers the oscillat ors. voltage is 1.8v nominal. the ground pins gnd are common to vddcore and vddio. the ground pin for vddpll is gndpll, and the gnd pin for vddosc is gndosc. see ?electrical characteristics? on page 928 for power consumption on the various supply pins. 4.2 power supply connections special considerations should be made when connecting the power and ground pins on a pcb. figure 4-1 shows how this should be done. figure 4-1. connecting analog power supplies avddusb avddpll avddosc agndusb agndpll agndosc vddcore vcc_1v8 3.3uh c54 0.10u c55 0.10u c56 0.10u
16 32054fs?avr32?09/09 at32ap7002 5. i/o line considerations 5.1 jtag pins the tms, tdi and tck pins have pull-up resistors. tdo is an output, driven at up to vddio, and have no pull-up resistor. the trst_n pin is used to initialize the embedded jtag tap controller when asserted at a low level. it is a schmitt input and integrates permanent pull-up resistor to vddio, so that it can be left unconnected for normal operations. 5.2 wake_n pin the wake_n pin is a schmitt trig ger input integr ating a permanent pull-up resistor to vddio. 5.3 reset_n pin the reset_n pin is a schmitt input and integrates a permanent pull-up resistor to vddio. as the product integrat es a power-on reset cell, the reset_n pin can be left unconnected in case no reset from the system needs to be applied to the product. 5.4 evti_n pin the evti_n pin is a schmitt input and integrates a non-programmable pull-up resistor to vddio. 5.5 twi pins when these pins are used for twi, the pins are open-drain outputs with slew-rate limitation and inputs with inputs with spike-filtering. when used as gpio-pins or used for other peripherals, the pins have the same characteristics as pio pins. 5.6 pio pins all the i/o lines integrate a programmable pull-up resistor . programming of this pull-up resistor is performed independently for each i/o line through the pio controllers. after reset, i/o lines default as inputs with pull-up resistors enabled, ex cept when indicated otherwise in the column ?reset state? of the pio controller multiplexing tables.
17 32054fs?avr32?09/09 at32ap7002 6. memories 6.1 embedded memories ? 32 kbyte sram ? implemented as two 16kbyte blocks ? single cycle access at full bus speed 6.2 physical memory map the system bus is implemented as an hsb bus matrix. all system bus addresses are fixed, and they are never remapped in any way, not even in boot. note that at32ap7002 by default uses segment translation, as described in the avr 32 architecture manual. the 32 bit physical address space is mapped as follows: accesses to unused areas returns an error result to the master requesting such an access. the bus matrix has the several masters and slaves. each master has its own bus and its own decoder, thus allowing a different memory mapping per master. the master number in the table below can be used to index the hmatrix contro l registers. for example, mcfg2 is associated with the hsb-hsb bridge. table 6-1. at32ap7002 physical memory map start address size device 0x0000_0000 64 mbyte ebi sram cs0 0x0400_0000 64 mbyte ebi sram cs4 0x0800_0000 64 mbyte ebi sram cs2 0x0c00_0000 64 mbyte ebi sram cs3 0x1000_0000 256 mbyte ebi sram/sdram cs1 0x2000_0000 64 mbyte ebi sram cs5 0x2400_0000 16 kbyte internal sram 0 0x2400_4000 16 kbyte internal sram1 0xff00_0000 4 kbyte lcdc configuration 0xff20_0000 1 kbyte dmaca configuration 0xff30_0000 1 mbyte usba data 0xffe0_0000 1 mbyte pba 0xfff0_0000 1 mbyte pbb
18 32054fs?avr32?09/09 at32ap7002 each slave has its own arbiter, thus allowing a different arbitration per slave. the slave number in the table below can be used to index the hmatrix control registers. for example, scfg3 is associated with pbb. table 6-2. hsb masters master 0 cpu dcache master 1 cpu icache master 2 hsb-hsb bridge master 3 isi dma master 4 usba dma master 5 lcd controller dma master 8 dmac master interface 0 master 9 dmac master interface 1 table 6-3. hsb slaves slave 0 internal sram 0 slave 1 internal sram1 slave 2 pba slave 3 pbb slave 4 ebi slave 5 usba data slave 6 lcdc configuration slave 7 dmaca configuration
19 32054fs?avr32?09/09 at32ap7002 7. peripherals 7.1 peripheral address map table 7-1. peripheral address mapping address peripheral name bus 0xff000000 lcdc lcd controller slave interface - lcdc hsb 0xff200000 dmaca dma controller slave interface- dmaca hsb 0xff300000 usba usb slave interface - usba hsb 0xffe00000 spi0 serial peripheral interface - spi0 pb a 0xffe00400 spi1 serial peripheral interface - spi1 pb a 0xffe00800 twi two-wire interface - twi pb a 0xffe00c00 usart0 universal synchronous asynchronous receiver transmitter - usart0 pb a 0xffe01000 usart1 universal synchronous asynchronous receiver transmitter - usart1 pb a 0xffe01400 usart2 universal synchronous asynchronous receiver transmitter - usart2 pb a 0xffe01800 usart3 universal synchronous asynchronous receiver transmitter - usart3 pb a 0xffe01c00 ssc0 synchronous serial controller - ssc0 pb a 0xffe02000 ssc1 synchronous serial controller - ssc1 pb a 0xffe02400 ssc2 synchronous serial controller - ssc2 pb a 0xffe02800 pioa parallel input/output 2 - pioa pb a 0xffe02c00 piob parallel input/output 2 - piob pb a 0xffe03000 pioc parallel input/output 2 - pioc pb a 0xffe03400 piod parallel input/output 2 - piod pb a
20 32054fs?avr32?09/09 at32ap7002 0xffe03800 pioe parallel input/output 2 - pioe pb a 0xffe03c00 psif ps2 interface - psif pb a 0xfff00000 pm power manager - pm pb b 0xfff00080 rtc real time counter- rtc pb b 0xfff000b0 wdt watchdog timer- wdt pb b 0xfff00100 eic external interrupt controller - eic pb b 0xfff00400 intc interrupt controller - intc pb b 0xfff00800 hmatrix hsb matrix - hmatrix pb b 0xfff00c00 tc0 timer/counter - tc0 pb b 0xfff01000 tc1 timer/counter - tc1 pb b 0xfff01400 pwm pulse width modulation controller - pwm pb b 0xfff02000 abdac audio bitstream dac - abdac pb b 0xfff02400 mci multimedia card interface - mci pb b 0xfff02800 ac97c ac97 controller - ac97c pb b 0xfff02c00 isi image sensor interface - isi pb b 0xfff03000 usba usb configuration interface - usba pb b 0xfff03400 smc static memory controller - smc pb b 0xfff03800 sdramc sdram controller - sdramc pb b 0xfff03c00 ecc error correcting code controller - ecc pb b table 7-1. peripheral address mapping (continued) address peripheral name bus
21 32054fs?avr32?09/09 at32ap7002 7.2 interrupt r equest signal map the various modules may output interrupt request signals. these signals are routed to the inter- rupt controller (intc). the interrupt controller supports up to 64 groups of interrupt requests. each group can have up to 32 interrupt request signals. all interrupt signals in the same group share the same autovector address and priority level. refer to the documentation for the individ- ual submodules for a description of the semantic of the different interrupt requests. the interrupt request signals in at32ap700 2 are connected to the intc as follows: table 7-2. interrupt request signal map group line signal 0 0 count-compare match 1 performance counter overflow 1 0 lcdc eof 1 lcdc ln 2 lcdc lstln 3 lcdc mer 4 lcdc owr 5 lcdc uflw 2 0 dmaca block 1 dmaca dstt 2dmaca err 3 dmaca srct 4dmaca tfr 3 0 spi 0 4 0 spi 1 50twi 6 0 usart0 7 0 usart1 8 0 usart2 9 0 usart3 10 0 ssc0 11 0 ssc1 12 0 ssc2 13 0 pioa 14 0 piob 15 0 pioc 16 0 piod 17 0 pioe 18 0 psif
22 32054fs?avr32?09/09 at32ap7002 7.3 dmaca handshake interface map the following table details the hardware handshake map between the dmaca and the peripher- als attached to it: : 19 0 eic0 1eic1 2eic2 3eic3 20 0 pm 21 0 rtc 22 0 tc00 1tc01 2tc02 23 0 tc10 1tc11 2tc12 24 0 pwm 27 0 abdac 28 0 mci 29 0 ac97c 30 0 isi 31 0 usba 32 0 ebi table 7-2. interrupt request signal map group line signal table 7-3. hardware handshaking connection request hardware handshaking interface mci rx 0 mci tx 1 abdac tx 2 ac97c channel a rx 3 ac97c channel a tx 4 ac97c channel b rx 5 ac97c channel b tx 6 external dma request 0 7 external dma request 1 8 external dma request 2 9 external dma request 3 10
23 32054fs?avr32?09/09 at32ap7002 7.4 clock connections 7.4.1 timer/counters each timer/counter channel can independently select an internal or external clock source for its counter: 7.4.2 usarts each usart can be connected to an internally divided clock: table 7-4. timer/counter clock connections timer/counter source name connection 0 internal timer_clock1 clk_osc32 timer_clock2 clk_pbb / 4 timer_clock3 clk_pbb / 8 timer_clock4 clk_pbb / 16 timer_clock5 clk_pbb / 32 external xc0 see section 7.7 xc1 xc2 1 internal timer_clock1 clk_osc32 timer_clock2 clk_pbb / 4 timer_clock3 clk_pbb / 8 timer_clock4 clk_pbb / 16 timer_clock5 clk_pbb / 32 external xc0 see section 7.7 xc1 xc2 table 7-5. usart clock connections usart source name connection 0 internal clk_div clk_pba / 8 1 2 3
24 32054fs?avr32?09/09 at32ap7002 7.4.3 spis each spi can be connected to an internally divided clock: 7.4.4 usba osc1 is connected to the usb hs phy and must be 12 mhz when using the usba. 7.5 external inte rrupt pin mapping external interrupt requests are connected to the following pins:: 7.6 nexus ocd aux port connections if the ocd trace system is enabled, the trace system will take control over a number of pins, irre- spectively of the pio configuration. two different ocd trace pi n mappings are possible, depending on the configuration of the ocd axs register. for details, see the avr32 ap techni- cal reference manual. table 7-6. spi clock connections spi source name connection 0 internal clk_div clk_pba / 32 1 table 7-7. external interrupt pin mapping source connection nmi_n pb24 extint0 pb25 extint1 pb26 extint2 pb27 extint3 pb28 table 7-8. nexus ocd aux port connections pin axs=0 axs=1 evti_n evti_n evti_n mdo[5] pb09 pc18 mdo[4] pb08 pc14 mdo[3] pb07 pc12 mdo[2] pb06 pc11 mdo[1] pb05 pc06 mdo[0] pb04 pc05 evto_n pb03 pb28 mcko pb02 pc02 mseo[1] pb01 pc01 mseo[0] pb00 pc00
25 32054fs?avr32?09/09 at32ap7002 7.7 peripheral multiplexing on io lines the at32ap7002 features five pio controllers, pioa to pioe, that multiplex the i/o lines of the peripheral set. each pio controller controls up to thirty-two lines. each line can be assigned to one of two peripheral functions, a or b. the tables in the following pages define how the i/o lines of the peripherals a and b are multiplexed on the pio controllers. note that some output only peripheral func tions might be duplicated within the tables. 7.7.1 pio controller a multiplexing table 7-9. pio controller a multiplexing ctbga196 i/o line peripheral a peripheral b j3 pa00 spi0 - miso ssc1 - rx_frame_sync j1 pa01 spi0 - mosi ssc1 - tx_frame_sync g6 pa02 spi0 - sck ssc1 - tx_clock j2 pa03 spi0 - npcs[0] ssc1 - rx_clock g5 pa04 spi0 - npcs[1] ssc1 - tx_data k1 pa05 spi0 - npcs[2] ssc1 - rx_data c9 pa06 twi - sda usart0 - rts e9 pa07 twi - scl usart0 - cts g7 pa08 psif - clock usart0 - rxd j6 pa09 psif - data usart0 - txd h6 pa10 mci - clk usart0 - clk k2 pa11 mci - cmd tc0 - clk0 k3 pa12 mci - data[0] tc0 - a0 m1 pa13 mci - data[1] tc0 - a1 h7 pa14 mci - data[2] tc0 - a2 n1 pa15 mci - data[3] tc0 - b0 k4 pa16 usart1 - clk tc0 - b1 p1 pa17 usart1 - rxd tc0 - b2 j7 pa18 usart1 - txd tc0 - clk2 l3 pa19 usart1 - rts tc0 - clk1 n2 pa20 usart1 - cts spi0 - npcs[3] l2 pa21 ssc0 - rx_frame_sync pwm - pwm[2] m2 pa22 ssc0 - rx_clock pwm - pwm[3] m3 pa23 ssc0 - tx_clock tc1 - a0 p2 pa24 ssc0 - tx_frame_sync tc1 - a1 l7 pa25 ssc0 - tx_data tc1 - b0 k7 pa26 ssc0 - rx_data tc1 - b1 p9 pa27 spi1 - npcs[3] tc1 - clk0 h9 pa28 pwm - pwm[0] tc1 - a2
26 32054fs?avr32?09/09 at32ap7002 7.7.2 pio controller b multiplexing l8 pa29 pwm - pwm[1] tc1 - b2 m8 pa30 pm - gclk[0] tc1 - clk1 p10 pa31 pm - gclk[1] tc1 - clk2 table 7-9. pio controller a multiplexing table 7-10. pio controller b multiplexing ctbga196 i/o line peripheral a peripheral b e11 pb00 isi - data[0] spi1 - miso d14 pb01 isi - data[1] spi1 - mosi c14 pb02 isi - data[2] spi1 - npcs[0] b14 pb03 isi - data[3] spi1 - npcs[1] a14 pb04 isi - data[4] spi1 - npcs[2] a13 pb05 isi - data[5] spi1 - sck b13 pb06 isi - data[6] mci - cmd[1] c13 pb07 isi - data[7] mci - data[4] a12 pb08 isi - hsync mci - data[5] b12 pb09 isi - vsync mci - data[6] c12 pb10 isi - pclk mci - data[7] a11 pb11 psif - clock[1] isi - data[8] b11 pb12 psif - data[1] isi - data[9] d12 pb13 ssc2 - tx_data isi - data[10] c11 pb14 ssc2 - rx_data isi - data[11] d11 pb15 ssc2 - tx_clock usart3 - cts a10 pb16 ssc2 - tx_frame_sync usart3 - rts b10 pb17 ssc2 - rx_frame_sync usart3 - txd a9 pb18 ssc2 - rx_clock usart3 - rxd c10 pb19 pm - gclk[2] usart3 - clk d10 pb20 abdac - data[1] ac97c - sdo b9 pb21 abdac - data[0] ac97c - sync a8 pb22 abdac - datan[1] ac97c - sclk b8 pb23 abdac - datan[0] ac97c - sdi h5 pb24 nmi_n dmaca - dmarq[0] l1 pb25 extint0 dmaca - dmarq[1] n9 pb26 extint1 usart2 - rxd j9 pb27 extint2 usart2 - txd k9 pb28 extint3 usart2 - clk n12 pb29 pm - gclk[3] usart2 - cts o14 pb30 pm - gclk[4] usart2 - rts
27 32054fs?avr32?09/09 at32ap7002
28 32054fs?avr32?09/09 at32ap7002 7.7.3 pio controller c multiplexing 7.7.4 pio controller d multiplexing table 7-11. pio controller c multiplexing ctbga196 i/o line peripheral a peripheral b a7 pc20 lcdc - hsync c8 pc21 lcdc - pclk b7 pc22 lcdc - vsync a6 pc23 lcdc - dval a5 pc28 lcdc - data[2] c7 pc29 lcdc - data[3] d8 pc30 lcdc - data[4] e8 pc31 lcdc - data[5] table 7-12. pio controller d multiplexing ctbga196 i/o line peripheral a peripheral b d2 pd00 lcdc - data[6] c2 pd01 lcdc - data[7] f4 pd04 lcdc - data[10] g1 pd05 lcdc - data[11] g3 pd06 lcdc - data[12] e5 pd07 lcdc - data[13] g2 pd08 lcdc - data[14] f5 pd09 lcdc - data[15] n3 pd12 lcdc - data[18] p3 pd13 lcdc - data[19] p4 pd14 lcdc - data[20] n4 pd15 lcdc - data[21] n5 pd16 lcdc - data[22] m4 pd17 lcdc - data[23]
29 32054fs?avr32?09/09 at32ap7002 7.7.5 io pins without multiplexing many of the external ebi pins are not controlled by the pio modules, but directly driven by the ebi. these pins have programmable pullup resistor s. these resistors are controlled by special function register 4 (sfr4) in the hmatrix. the pullup on the lines multiplexed with pio is controlled by the appropriate pio control register. this sfr can also control compactflash, smartmedia or nandflash support, see the ebi chap- ter for details 7.7.5.1 hmatrix sfr4 ebi control register name: hmatrix_sfr4 access type: read/write ? cs1a: chip select 1 assignment 0 = chip select 1 is assigned to the static memory controller. 1 = chip select 1 is assign ed to the sdram controller. ? cs3a: chip select 3 assignment 0 = chip select 3 is only assigned to the static memory contro ller and ncs3 behaves as defined by the smc. 1 = chip select 3 is assigned to the static memory controller and the nand flash/smartmedia logic is activated. ? cs4a: chip select 4 assignment 0 = chip select 4 is assigned to the stat ic memory controller and ncs4, ncs5 and ncs6 behave as defined by the smc. 1 = chip select 4 is assigned to the static memory controller and the compactflash logic is activated. ? cs5a: chip select 5 assignment 0 = chip select 5 is assigned to the stat ic memory controller and ncs4, ncs5 and ncs6 behave as defined by the smc. 1 = chip select 5 is assigned to the static memory controller and the compactflash logic is activated. 31 30 29 28 27 26 25 24 ???????? 23 22 21 20 19 18 17 16 ???????? 15 14 13 12 11 10 9 8 ???????ebi_dbpuc 76543210 ? ? ebi_cs5a ebi_cs4a ebi_cs3a ? ebi_cs1a -
30 32054fs?avr32?09/09 at32ap7002 accessing the address space reserved to ncs5 and ncs6 may lead to an unpredictable outcome. ? ebi_dbpuc: ebi data bus pull-up control 0: ebi d[15:0] are internally pulled up to the vddio power supply. the pull-up resistors are enabled after reset. 1: ebi d[15:0] are not internally pulled up. table 7-13. io pins without multiplexing i/o line function px00 ebi - data[0] px01 ebi - data[1] px02 ebi - data[2] px03 ebi - data[3] px04 ebi - data[4] px05 ebi - data[5] px06 ebi - data[6] px07 ebi - data[7] px08 ebi - data[8] px09 ebi - data[9] px10 ebi - data[10] px11 ebi - data[11] px12 ebi - data[12] px13 ebi - data[13] px14 ebi - data[14] px15 ebi - data[15] px16 ebi - addr[0] px17 ebi - addr[1] px18 ebi - addr[2] px19 ebi - addr[3] px20 ebi - addr[4] px21 ebi - addr[5] px22 ebi - addr[6] px23 ebi - addr[7] px24 ebi - addr[8] px25 ebi - addr[9] px26 ebi - addr[10] px27 ebi - addr[11] px28 ebi - addr[12] px29 ebi - addr[13] px30 ebi - addr[14] px31 ebi - addr[15]
31 32054fs?avr32?09/09 at32ap7002 px32 ebi - addr[16] px33 ebi - addr[17] px34 ebi - addr[18] px35 ebi - addr[19] px36 ebi - addr[20] px37 ebi - addr[21] px38 ebi - addr[22] px39 ebi - ncs[0] px40 ebi - ncs[1] px41 ebi - ncs[3] px42 ebi - nrd px43 ebi - nwe0 px44 ebi - nwe1 px45 ebi - nwe3 px46 ebi - sdck px47 ebi - sdcke px48 ebi - ras px49 ebi - cas px50 ebi - sdwe px51 ebi - sda10 px52 ebi - nandoe px53 ebi - nandwe table 7-13. io pins without multiplexing (continued)
32 32054fs?avr32?09/09 at32ap7002 7.8 peripheral overview 7.8.1 external bus interface ? optimized for application memory space support ? integrates three external memory controllers: ? static memory controller ? sdram controller ? ecc controller ? additional logic for nand flash/smartmedia tm and compactflash tm support ? smartmedia support: 8-bit as well as 16-bit devices are supported ? compactflash support: all modes (attribute memory, common memory, i/o, true ide) are supported but the signal s _iois16 (i/o and true ide modes) and _ata sel (true ide mode) are not handled. ? optimized external bus: ? 16- or 32-bit data bus ? up to 26-bit address bus, up to 64-mbytes addressable ? optimized pin multiplexing to redu ce latencies on external memories ? up to 6 chip selects, configurable assignment: ? static memory controller on ncs0 ? sdram controller or static memory controller on ncs1 ? static memory controller on ncs2 ? static memory controller on ncs 3, optional nand flash/smartmedia tm support ? static memory controller on ncs 4 - ncs5, optional compactflash tm support 7.8.2 static memory controller ? 6 chip selects available ? 64-mbyte address space per chip select ? 8-, 16- or 32-bit data bus ? word, halfword, byte transfers ? byte write or by te select lines ? programmable setup, pulse and hold ti me for read signals per chip select ? programmable setup, pulse and hold time for write signals per chip select ? programmable data float time per chip select ? compliant with lcd module ? external wait request ? automatic switch to slow clock mode ? asynchronous read in page mode supporte d: page size ranges from 4 to 32 bytes 7.8.3 sdram controller ? numerous configurations supported ? 2k, 4k, 8k row address memory parts ? sdram with two or four internal banks ? sdram with 16- or 32-bit data path ? programming facilities ? word, half-word, byte access ? automatic page break when memory boundary has been reached ? multibank ping-pong access ? timing parameters specified by software ? automatic refresh operation, refresh rate is programmable
33 32054fs?avr32?09/09 at32ap7002 ? energy-saving capabilities ? self-refresh, power-down and deep power modes supported ? supports mobile sdram devices ? error detection ? refresh error interrupt ? sdram power-up initialization by software ? cas latency of 1, 2, 3 supported ? auto precharge command not used 7.8.4 error corrected code controller ? hardware error corrected code (ecc) generation ? detection and correction by software ? supports nand flash and smartmedia ? devices with 8- or 16-bit data path. ? supports nand flash/smartmedia with page size s of 528, 1056, 2112 and 4224 bytes, specified by software 7.8.5 serial peripheral interface ? supports communication with serial external devices ? four chip selects with extern al decoder support allow co mmunication with up to 15 peripherals ? serial memories, such as da taflash? and 3-wire eeproms ? serial peripherals, such as adcs, dacs, l cd controllers, can controllers and sensors ? external co-processors ? master or slave serial peripheral bus interface ? 8- to 16-bit programmable da ta length per chip select ? programmable phase and polarity per chip select ? programmable transfer delays between consecutive transfers and between clock and data per chip select ? programmable delay between consecutive transfers ? selectable mode fault detection ? very fast transfers supported ? transfers with baud rates up to mck ? the chip select line may be left active to speed up transfer s on the same device 7.8.6 two-wire interface ? compatibility with standard two-wire serial memory ? one, two or three bytes for slave address ? sequential read/write operations
34 32054fs?avr32?09/09 at32ap7002 7.8.7 usart ? programmable baud rate generator ? 5- to 9-bit full-duplex synchronous or asynchronous serial communications ? 1, 1.5 or 2 stop bits in a synchronous mode or 1 or 2 stop bits in synchronous mode ? parity generation and error detection ? framing error detection, overrun error detection ? msb- or lsb-first ? optional break generation and detection ? by 8 or by-16 over-sampling receiver frequency ? hardware handshaking rts-cts ? receiver time-out and transmitter timeguard ? optional multi-drop mode with address generation and detection ? optional manchester encoding ? rs485 with driver control signal ? iso7816, t = 0 or t = 1 protocols for interfacing with smart cards ? nack handling, error counter with repetition and iteration limit ? irda modulation and demodulation ? communication at up to 115.2 kbps ? test modes 46 ? remote loopback, local loopback, automatic echo 7.8.8 serial synchronous controller ? provides serial synchronous communication links used in audio and tel ecom applications (with codecs in master or slave modes, i2s, tdm buses, magnetic card reader, etc.) ? contains an independent receiver and transmitter and a common clock divider ? offers a configurable frame sync and data length ? receiver and transmitter can be programmed to st art automatically or on detection of different event on the frame sync signal ? receiver and transmitter include a data signal, a cloc k signal and a frame synchronization signal 7.8.9 ac97 controller ? compatible with ac97 comp onent specification v2.2 ? capable to interface with a single analog front end ? three independent rx channels and three independent tx channels ? one rx and one tx channel dedicated to the ac97 analog front end control ? one rx and one tx channel for data transfers, connected to the dmaca ? one rx and one tx channel for data transfers, connected to the dmaca ? time slot assigner allowing to assign up to 12 time slots to a channel ? channels support mono or stereo up to 20 bit sample length - variable sampling rate ac97 codec interface (48khz and below)
35 32054fs?avr32?09/09 at32ap7002 7.8.10 audio bitstream dac ? digital stereo dac ? oversampled d/a conversion architecture ? oversampling ratio fixed 128x ? fir equalization filter ? digital interpolation filter: comb4 ? 3rd order sigma-delta d/a converters ? digital bitstream outputs ? parallel interface ? connected to dma controller for backgrou nd transfer without cpu intervention 7.8.11 timer counter ? three 16-bit timer counter channels ? wide range of functions including: ? frequency measurement ? event counting ? interval measurement ? pulse generation ? delay timing ? pulse width modulation ? up/down capabilities ? each channel is user-conf igurable and contains: ? three external clock inputs ? five internal clock inputs ? two multi-purpose input/output signals ? two global registers that ac t on all three tc channels 7.8.12 pulse width modulation controller ? 4 channels, one 16-bit counter per channel ? common clock generator, providing thirteen different clocks ? a modulo n counter providing eleven clocks ? two independent linear dividers working on modulo n counter outputs ? independent channel programming ? independent enable disable commands ? independent clock ? independent period and duty cycle, with double bufferization ? programmable selection of the output waveform polarity ? programmable center or left aligned output waveform
36 32054fs?avr32?09/09 at32ap7002 7.8.13 multimedia card interface ? 2 double-channel multimedia card interface, al lowing concurrent transfers with 2 cards ? compatibility with multimedia card specification version 2.2 ? compatibility with sd memory card specification version 1.0 ? compatibility with sdio specification version v1.0. ? cards clock rate up to master clock divided by 2 ? embedded power management to slow down clock rate when not used ? each mci has two slot, each supporting ? one slot for one multimediacard bus (up to 30 cards) or ?one sd memory card ? support for stream, block and multi-block data read and write 7.8.14 ps/2 interface ? peripheral bus slave ? ps/2 host ? receive and transmit capability ? parity generation and error detection ? overrun error detection 7.8.15 usb interface ? supports hi (480mbps) and full (12mbps) speed communication ? compatible with the usb 2.0 specification ? utmi compliant ? 7 endpoints ? embedded dual-port ram for endpoints ? suspend/resume logic (command of utmi) ? up to three memory banks for endpoints (not for control endpoint) ? 4 kbytes of dpram 7.8.16 lcd controller ? single and dual scan color and monoch rome passive stn lcd panels supported ? single scan active tft lcd panels supported ? 4-bit single scan, 8-bit single or dual scan, 16-bit dual scan stn interfaces supported ? up to 24-bit single scan tft interfaces supported ? up to 16 gray levels for mono stn and up to 4096 colors for color stn displays ? 1, 2 bits per pixel (palletized), 4 bits per pixel (non-palletized) for mono stn ? 1, 2, 4, 8 bits per pixel (palletized), 16 bits per pixel (non-palletized) for color stn ? 1, 2, 4, 8 bits per pixel (palletized), 16 , 24 bits per pixel (non-palletized) for tft ? single clock domain architecture ? resolution supported up to 2048x2048 ? 2d-dma controller for manageme nt of virtual frame buffer ? allows management of frame buffer larger than the screen size and moving the view over this virtual frame buffer ? automatic resynchronization of the fram e buffer pointer to prevent flickering ? configurable coefficien ts with flexible fixe d-point representation.
37 32054fs?avr32?09/09 at32ap7002 ? 7.8.17 image sensor interface ? itu-r bt. 601/656 8-bit mode external interface support ? support for itu-r bt.656-4 sav and eav synchronization ? vertical and horizontal re solutions up to 2048 x 2048 ? preview path up to 640*480 ? support for packed data formatting for ycbcr 4:2:2 formats ? preview scaler to generate smaller size image 50 ? programmable frame capture rate
38 32054fs?avr32?09/09 at32ap7002 8. boot sequence this chapter summarizes the boot sequence of the at32ap7002. the behaviour after power-up is controlled by the power manager. 8.1 starting of clocks after power-up, the device will be held in a rese t state by the power-on reset (por) circuitry until the voltage has reached the power-on reset ri sing threshold value (see electrical character- istics for details). this ensure s that all critical parts of the device are properly reset. once the power-on reset is comp lete, the device will use the xin0 pin as clock source. xin0 can be connected either to an external clock, or a crystal. the oscen_n pin is connected either to vdd or gnd to inform the power manager on how the xin0 pin is connected. if xin0 receives a signal from a crystal, dedicated circuitry in the power manager keeps the part in a reset state until the oscillator connected to xin0 has settled. if xin0 receives an external clock, no such set- tling delay is applied. on system start-up, the plls are disabled. all clocks to all modules are running. no clocks have a divided frequency, all parts of the system recieves a clock with the same frequency as the xin0 clock. note that the power-on reset will release reset at a lower voltage threshold than the minimum specified operating voltage. if the voltage is not guaranteed to be stable by the time the device starts executing, an external brown-out reset circuit should be used. 8.2 fetching of initial instructions after reset has been released, the avr32ap cpu starts fetching instructions from the reset address, which is 0xa000_0000. this address lies in the p2 segment, which is non-translated, non-cacheable, and permanently mapped to the physical address range 0x0000_0000 to 0x2000_0000. this means that the instruction being fetched from virtual address 0xa000_0000 is being fetched from physical address 0x0000_0000. physical address 0x0000_0000 is mapped to ebi sram cs0. this is the external memory the device boots from. the code read from the sram cs0 memory is free to configure the system to use for example the plls, to divide the frequency of the clock routed to some of the peripherals, and to gate the clocks to unused peripherals.
39 32054fs?avr32?09/09 at32ap7002 9. ordering information table 9-1. ordering information ordering code package package type packing temperature operating range AT32AP7002-CTUR ctbga196 green reel industrial (-40c to 85c) at32ap7002-ctut ctbga196 green tray industrial (-40c to 85c)
40 32054fs?avr32?09/09 at32ap7002 10. errata 10.1 rev. c 1. spi fdiv option does not work selecting clock signal using fdiv = 1 does not work as specified. fix/workaround do not set fdiv = 1. 2. spi chip select 0 bits field overrides other chip selects the bits field for chip select 0 overrides bits fields for other chip selects. fix/workaround update chip select 0 bits field to the relevant settings before transmit ting with chip selects other than 0. 3. spi lastxfer may be overwritten when peripheral select (ps) = 0, the lastxfer -bit in the transmit data register (tdr) should be internally discared. this fails and may cause problems during dma transfers. transmitting data using the pdc when ps=0, the size of the transferred data is 8- or 16-bits. the upper 16 bits of the tdr will be written to a random value. if chip select active after transfer (csaat) = 1, the behavior of the chip select will be unpredictable. fix/workaround - do not use csaat = 1 if ps = 0 - use gpio to control chip select lines - select ps=1 and store data for pcs and lastxfer for each data in transmit buffer. 4. spi lastxfer ove rrides chip select the lastxfer bit overrides chip select input when ps = 0 and csaat is used. fix/workaround - do not use the csaat - use gpio as chip select input - select ps = 1. transfer 32-bit with correct lastxfer settings. 5. mmc data write operation with less than 12 bytes is impossible. mci data write operation with less than 12 bytes is impossible. the data write operation with a number of bytes less than 12 leaves the internal mci fifo in an inconsistent state. subsequent reads and writes will not functi on properly. fix/workaround always transfer 12 or more bytes at a time. if less than 12 bytes are transferred, the only recovery mechanism is to perform a software reset of the mci. 6. mmc sdio interrupt only works for slot a if 1-bit data bus width and on other slots than slot a, the sdio interrupt can not be cap- tured.
41 32054fs?avr32?09/09 at32ap7002 fix/workaround use slot a. 7. psif txen/rxen may disable the transmitter/receiver writing a '0' to rxen will disable the receiver. writing '0' to txen will disable the transmitter. fix/workaround when accessing the ps/2 control register alwa ys write '1' to rxen to keep the receiver enabled, and write '1' to txen to keep the transmitter enabled. 8. psif txrdy interrupt corrupts transfers when writing to the transmit holding register (thr), the da ta will be transfer red to the data shift register immediately, regardless of the state of the data shift register. if a transfer is ongoing, it will be inte rrupted and a new transfer will be st arted with the new data written to thr. fix/workaround use the txempty-interrupt instead of the txrdy-interrupt to update the thr. this ensures that a transfer is completed. 9. lcd memory error interupt does not work writing to the merit-bit in the lcd interrupt test register (itr) does not cause an interrupt as intended. the meric-bit in the lcd inte rrupt clear register (icr) cannot be written. this means that if the meris-bit in isr is set, it cannot be cleared. fix/workaround memory error interrupt should not be used. 10. pwm counter restarts at 0x0001 the pwm counter restarts at 0x0001 and not 0x0000 as specified. because of this the first pwm period has one more clock cycle. fix/workaround - the first period is 0x0000, 0x0001, ..., period - consecutive periods are 0x0001, 0x0002, ..., period 11. pwm channel interrupt enabling triggers an interrupt when enabling a pwm channel that is configured with center aligned period (calg=1), an interrupt is signalled. fix/workaround when using center aligned mode, enable the channel and read the status before channel interrupt is enabled. 12. pwm update period to a 0 value does not work it is impossible to update a period equal to 0 by the using the pwm update register (pwm_cupd). fix/workaround do not update the pwm_cupd register with a value equal to 0. 13. pwm channel status may be wrong if disabled before a period has elapsed
42 32054fs?avr32?09/09 at32ap7002 before a pwm period has elapsed, the read channel status may be wrong. the chidx-bit for a pwm channel in the pwm enable register will read '1' fo r one full pwm period even if the channel was disabled before the period elapsed. it will then read '0' as expected. fix/workaround reading the pwm channel status of a disabled channel is only correct after a pwm period 14. twi transfer error without ack if the twi does not receive an ack from a slave during the address+r/w phase, no bits in the status register will be set to indicate this. hence, the transf er will neve r complete. fix/workaround to prevent errors due to missing ack, the software should use a timeout mechanism to ter- minate the transfer if this happens. 15. ssc can not transmit or receive data the ssc can not transmit or receive data when cks = ckdiv and cko = none in tcmr or rcmr respectively. fix/workaround set cko to a value that is not "none" and enable the pio with output driver disabled on the tk/rk pin. 16. usart - rxbreak flag is not correctly handled the frame_error is set instead of the rxbr eak when the break character is located just after the stop bit( s) in asynchronous mode. fix/workaround the transmitting uart must set timeguard greater than 0. 17. usart - manchester encoding/decoding is not working. manchester encoding/decoding is not working. fix/workaround do not use manchester encoding. 18. spi - disabling spi has no effect on tdre flag. disabling spi has no effect on tdre whereas the write data command is filtered when spi is disabled. this means that as soon as the spi is disabled it becomes impossible to reset the tdre flag by writing in the spi_tdr. so if the spi is disabled during a pdc transfer, the pdc will continue to write data in the spi_tdr (as tdre keeps high) ti ll its buffer is empty, and all data written after the disable command is lost. fix/workaround disable pdc, 2 nop (minimum), disable spi. when you want to continue the transfer: enable spi, enable pdc. 19. spi disable does not work in slave mode. spi disable does not work in slave mode. fix/workaround read the last received data, then perform a software reset.
43 32054fs?avr32?09/09 at32ap7002 21. scc - first data transmitted after reset is not datdef. in the first frame transmitted, the first transm itted data that follows the frame synchro is 0, not datdef. this happens when: 1. pdc is disabled 2. reset the ssc 3. configure the ssc with a transmit start condition different from continuous (start = 0) 4. datdef = 1 5. enable the ssc in transmission. this trouble only appears after a reset and it is only the first frame is affected. fix/workaround use the pdc to fill the thr afte r the enable of the ssc and be fore the start of the frame. 21. mci - false data time out error dtoe may occur. if a small block (5 bytes) is read through the read_single_block command (cmd17), the flag notbusy will be set and a false data timeout error dtoe occurs. fix/workaround none. 22. sdram - self-refresh mode if entry in self-refresh mode is followed by sdram access and auto-refresh event, trc tim- ing is not checked for auto_refresh sequence. fix/workaround set the value of tras field in user interface with trc+1. 23. spi - no tx underrun flag available there is no tx underrun flag av ailable, therefore in slave mode there is no way to be informed of a character lost in transmission. fix/workaround pdc/pdca transfers: none. manual transfers (no pdc and tx slave only): read the rhr every time the thr is written. the ovrs flag of the status register will track any underrun on the tx side. 24. hmatrix - fixed priority arbitration does not work fixed priority arbitration does not work. fix/workaround use round-robin arbitration instead. 25. osc32 is not available for rtc, wdt, timers and usarts at startup right after startup the osc32 clock to internal modules is not valid. the osc32 clock will be valid for use approximately 128 osc32 cycles af ter the the first instruction is executed. this has consequences if you are planning to use the rtc, wdt, going into sleep mode and usarts with sck and tcs with timer_clock0.
44 32054fs?avr32?09/09 at32ap7002 fix/workaround before executing any code the user should enable the rtc with the smallest prescaler and poll that the rtc is counting before doing anything in your program. another way to ensure that the osc32 is valid is to use interrupts with top=1. example: //reset the counter register avr32_rtc.val = 0x0; //enable the rtc with the smallest prescaler avr32_rtc.ctrl = 0x1; //wait until the value increases while(avr32_rtc.val == 0); 26. spi can generate a false rxready signal in slave mode in slave mode the spi can generate a false rxready signal during enabling of the spi or dur- ing the first transfer. fix/workaround 1. set slave mode, set required cpol/cpha 2. enable spi 3. set the polarity cpol of the line in the opposite value of the required one 4. set the polarity cpol to the required one. 5. read the rxholding register transfers can now begin and rxr eady will now behave as expected. 27. ebi address lines 23, 24, and 25 are pulled up when booting up after reset the ebi address lines 23, 24 and 25 are tristated with pullups. booting from a flash larger than 8 mb using these lines will fa il, as the flash will be accessed with these address bits set. fix/workaround add external pulldown resistors (5 k ) on these lines if booting from a flash larger than 8 mb using these address lines. 28. ssc - additional delay on td output a delay from 2 to 3 system clock cycles is added to td output when: tcmr.start = receive start, tcmr.sttdly = more than zero, rcmr.start = start on falling edge / start on rising edge / start on any edge rfmr.fsos = none (input) fix/workaround none. 29. ssc - tf output is not correct tf output is not correct (at least emitted one serial clock cycle later than expected) when: tfmr.fsos = driven low during data transfer/ driven high during data transfer
45 32054fs?avr32?09/09 at32ap7002 tcmr.start = receive start rfmr.fsos = none (input) rcmr.start = any on rf (edge/level) fix/workaround none. 30. usart - txd signal is floating in modem and hardware handshaking mode the txd signal is floating in modem and hardware handshaking mode, but should be pulled up. fix/workaround enable pullup on this line in the pio. 31. pwm - impossible to update a period equal to 0 by using the cupd register it is impossible to update a period equal to 0 by the using of the update register (cupd). fix/workaround to update a period equal to 0, write directly to the cprd register. 32. wdt clear is blocked after wdt reset a watchdog timer event will, after reset, block writes to the wdt_clear register, prevent- ing the program to clear the next watchdog timer reset. fix/workaround if the rtc is not used a write to avr32_rtc.ctrl.pclr = 1, instead of writing to avr32_wdt.clr, will reset the prescaler and th us prevent the watchd og event from happen- ing. this will render the rtc useless, but prevents wdt reset because the rtc and wdt share the same prescaler. anot her sideeffect of this is that the watchdog timeout period will be half the expected timeout period. if the rtc is used one can disable the watchdog timer (wdt) after a wdt reset has occured. this will prev ent the wdt resetting the system. to make the wdt functional again a hard reset (power on reset or reset_n) must be applied. if you still want to use the wdt after a wdt reset a small code can be inserted at the startup checking the avr32_pm.rcause register for wdt reset and use a gpio pin to reset the system. this method requires that one of the gpio pins ar e available and connected externally to the reset_n pin. after the gpio pin has pulled down the reset line the gpio will be reset and leave the pin tristated with pullup. 33. usart - the dcd signal is active high from the usart, but should be active low the dcd signal is active high from the usart, but should be active low. fix/workaround an inverter should be added on this line on the pcb. 34. mci transmit data regi ster (tdr) fifo corruption if the number of bytes to be transmitted by the mci is not a multiple of 4, the transmit data register (tdr) first in first ou t data buffer control logic w ill become corrupted when trans- mit data is written to the tdr as 32-bit values. fix/workaround
46 32054fs?avr32?09/09 at32ap7002 configure the mci mode register (mr) to accept 8-bit data input by writing a 1 to bit 13 (fbyte), and transfer each byte of the transmit data to tdr by right aligning the useful value. this allows the number of bytes transferred into the tdr to match the number set up in the bcnt field of the mci block register (blkr). 35. unreliable branch folding in certain situations, branch folding does not work as expected. fix/workaround write 0 to cpucr.fe before executing any branch instructions after reset. 36. usb pll jitter may cause packet loss during usb hi-speed transmission the usb hi-speed pll accuracy is not suffic ient for isochronous usb hi-speed transmis- sion and may cause packet loss. the obse rved bit-loss is typically < 125 ppm. fix/workaround do not use isochronous mode if absolute data accuracy is critical. 10.2 rev. b not sampled. 10.3 rev. a not sampled.
47 32054fs?avr32?09/09 at32ap7002 11. datasheet revision history please note that the referring page numbers in th is section are referred to this document. the referring revision in this section are referring to the document revision. 11.1 rev. f 09/09 11.2 rev. e 09/09 11.3 rev. d 09/07 1. updated ?errata? . 1. updated ?errata? . 1. pio controller c multiplexing table updated in ?peripherals? on page 75 ?. 2. added section ?usba? on page 81 in clock connections in ?peripherals? on page 75 . 3. usba feature list updated in ?peripherals? on page 75 . 4. renamed clk_slow to clk_osc32 in table 9-4 on page 80 . 5 updated organisation of user interface in ?hsb bus matrix (hmatrix)? on page 142 . 6. updated special bus granting mechanism in ?hsb bus matrix (hmatrix)? on page 142 . 7. added product dependencies in ?dma controller (dmaca)? on page 174 . 8. added product dependencies in ?peripheral dma controller (pdc)? on page 233 . 9. added description of multi-drive in ?parallel input/output controller (pio)? on page 249 . 10 added mder/mddr/mdsr to pin logic diagram in ?parallel input/output controller (pio)? on page 249 . 11. spi pins must be enabled to use local loopback. 12. updated description of the ovres bit in ?spi status register? on page 310 . 13. updated bit description of txempty in the ?usart channel status register? on page 432 . 14. number of chip select lines updatedin figur es and tables, changed from 8 to 6 in ?static memory controller (smc)? on page 489 . 15. made the mdr register read/write instead of read in ?sdram controller (sdramc)? on page 532 . 16. removed the pwsen and pwsdis bits from the ?mci control register? on page 585 . 17. added pdcfbyte and removed the pwsdiv bits from the ?mci mode register? on page 586 . 18. added note about reading the status register clears the interrupt flag in ?timer/counter (tc)? on page 740 . 19. added debug operation to product dependencies in ?timer/counter (tc)? on page 740 .
48 32054fs?avr32?09/09 at32ap7002 11.4 rev. c 07/07 11.5 rev. b 04/07 20. added debug operation to product dependencies in ?pulse width modulation controller (pwm)? on page 774 . 21. consistently used the term lcdc core clock through the document when referring to the generic clock that drives the lcd core and is used to generate pclk and the other lcd synchronization signals. 22. updated typos in ?lcd controller (lcdc)? on page 800 . 23. rewritten the register configuration guide and renamed it ?register configuration example? in ?lcd controller (lcdc)? on page 800 . 24. updated formula for pixel clock in ?lcd control register 1? on page 840 . 25. updated hozval description in ?lcd frame configuration register? on page 845 . 26. updated ?pll characteristics? on page 933 . 27. updated ?errata? on page 40 . 1. updated ?part description? on page 2 . 2. pc signals removed in ?signals description? on page 5 3. usb signals updated in ?signals description? on page 5 . 4. the px0 - px53 signals added in ?signals description? on page 5 . 5. sdcs signals removed from pio controller multiplexing tables in ?peripherals? on page 79 . 6. mac references removed form tables in ?memories? on page 77 . 7. mac controller references removed in ?peripheral overview? on page 94 . 8. sdcs1 signal removed from figures and tables, and sdcs0 renamed to sdcs in ?external bus interface (ebi)? on page 147 . 9. smartmedia renamed to nand flash in some description to avoid confusion in ?external bus interface (ebi)? on page 147 . 10. updated application block diagram in figure 1-2 on page 1 . 11. updated the reset state of the smc mode register in table 27-9 on page 523 . 12. updated ?mechanical characteristics? on page 927 . 13. updated pad parameters in ?dc characteristics? on page 928 . 14. updated ?power consumption by peripheral in active mode? on page 930 , lcd and macb excluded. 15. updated pad parameters in ?clock characteristics? on page 931 . 16. updated ?usb transceiver characteristics? on page 934 . 17. updated ?ebi timings? on page 939 . 1. updated ?features? on page 1 . 2. updated tables in ?signals description? on page 4 . 3. updated table 9-2 on page 77 , table 9-9 on page 82 , and table 9-10 on page 83 in the ?peripherals? on page 75 . 4. updated module names and abbreviations through the datasheet.
49 32054fs?avr32?09/09 at32ap7002 11.6 rev. a 02/07 1. initial revision.
i 32054fs?avr32?09/09 at32ap7002 table of contents features ................ ................ .............. ............... .............. .............. ............ 1 1 part description ......... ................ ................. ................ ................. ............ 2 2 blockdiagram ............. ................ ................. ................ ................. ............ 4 2.1package and pinoutavr32ap7002 ..........................................................................8 3 signals description ............ .............. ............... .............. .............. .......... 10 4 power considerations ........ .............. ............... .............. .............. .......... 15 4.1power supplies .......................................................................................................15 4.2power supply connections .....................................................................................15 5 i/o line considerations ...... .............. ............... .............. .............. .......... 16 5.1jtag pins ................................................................................................................16 5.2wake_n pin ............. ................. ................ ................ ................ ................ .............16 5.3reset_n pin ............ ................. ................ ................ ................ ................ .............16 5.4evti_n pin ..............................................................................................................16 5.5twi pins ..................................................................................................................1 6 5.6pio pins ................................................................................................................... 16 6 memories ............... .............. .............. ............... .............. .............. .......... 17 6.1embedded memories ..............................................................................................17 6.2physical memory map .............................................................................................17 7 peripherals ............ .............. .............. ............... .............. .............. .......... 19 7.1peripheral address map ..........................................................................................19 7.2interrupt request signal map ..................................................................................21 7.3dmaca handshake interface map .........................................................................22 7.4clock connections ..................................................................................................23 7.5external interrupt pin mapping ................................................................................24 7.6nexus ocd aux port connections .........................................................................24 7.7peripheral multiplexing on io lines ..........................................................................25 7.8peripheral overview .................................................................................................32 8 boot sequence ............. ................. ................ ................. .............. .......... 38 8.1starting of clocks .....................................................................................................38 8.2fetching of initial instructions ..................................................................................38 9 ordering information .......... .............. ............... .............. .............. .......... 39
ii 32054fs?avr32?09/09 at32ap7002 10 errata ............. ................ ................. ................ ................. .............. .......... 40 10.1rev. c ...................................................................................................................4 0 10.2rev. b .................................................................................................................... 46 10.3rev. a .................................................................................................................... 46 11 datasheet revision history .. .............. .............. .............. .............. ........ 47 11.1rev. f 09/09 ..........................................................................................................47 11.2rev. e 09/09 ..........................................................................................................47 11.3rev. d 09/07 .........................................................................................................47 11.4rev. c 07/07 .........................................................................................................48 11.5rev. b 04/07 ..........................................................................................................48 11.6rev. a 02/07 ..........................................................................................................49 table of contents.......... ................. ................ ................. ................ ........... i
32054fs?avr32?09/09 headquarters international atmel corporation 2325 orchard parkway san jose, ca 95131 usa tel: 1(408) 441-0311 fax: 1(408) 487-2600 atmel asia unit 1-5 & 16, 19/f bea tower, millennium city 5 418 kwun tong road kwun tong, kowloon hong kong tel: (852) 2245-6100 fax: (852) 2722-1369 atmel europe le krebs 8, rue jean-pierre timbaud bp 309 78054 saint-quentin-en- yvelines cedex france tel: (33) 1-30-60-70-00 fax: (33) 1-30-60-71-11 atmel japan 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel: (81) 3-3523-3551 fax: (81) 3-3523-7581 product contact web site www.atmel.com technical support avr32@atmel.com sales contact www.atmel.com/contacts literature requests www.atmel.com/literature disclaimer: the information in this document is provided in connection with atmel products. no license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of atmel products. except as set forth in atmel?s terms and condi- tions of sale located on atmel?s web site, atmel assumes no li ability whatsoever and disclaims any express, implied or statutor y warranty relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particu lar purpose, or non-infringement. in no event shall atmel be liable for any direct, indirect, consequential, punitive, special or i nciden- tal damages (including, without limitation, damages for loss of profits, business interruption, or loss of information) arising out of the use or inability to use this document, even if atme l has been advised of the possibility of such damages. atmel makes no representations or warranties with respect to the accuracy or comp leteness of the contents of this document and reserves the rig ht to make changes to specifications and product descriptions at any time without notice. atmel does not make any commitment to update the information contained her ein. unless specifically provided otherwise, atmel products are not suitable for, and shall not be used in, automotive applications. atmel?s products are not int ended, authorized, or warranted for use as components in applications in tended to support or sustain life. ? 2009 atmel corporation. all rights reserved. atmel ? , atmel logo and combinations thereof, avr ? , avr ? logo and others are registered trade- marks or trademarks of atmel corporation or its subsidiari es. other terms and product names may be trademarks of others.

▲Up To Search▲

Price & Availability of AT32AP7002-CTUR

	To Download AT32AP7002-CTUR Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .